Fixes RamUsageEstimator performance issue in tiered caching framework#16
Open
peteralfonsi wants to merge 1 commit intofeature/tiered-cachingfrom
Open
Fixes RamUsageEstimator performance issue in tiered caching framework#16peteralfonsi wants to merge 1 commit intofeature/tiered-cachingfrom
peteralfonsi wants to merge 1 commit intofeature/tiered-cachingfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Computes the estimated RAM size of IRC Key objects and IndicesService.IndexShardCacheEntity objects just once, rather than every time one gets instantiated. This was causing ~5% performance overhead in tiered caching relative to baseline. These classes were static before our tiered caching changes, so this should not cause any issues.
Related Issues
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.